Conversation
Replace non-breaking-space indentation in generated API reference tables with visible tree prefixes (`├─`, `└─`, `│`) so nested fields are easier to scan. Regenerated affected API reference docs with the updated template. --- _Generated with `mux` • Model: `openai:gpt-5.3-codex` • Thinking: `xhigh` • Cost: `$0.56`_ <!-- mux-attribution: model=openai:gpt-5.3-codex thinking=xhigh costs=0.56 -->
|
@codex review |
![chatgpt-codex-connector[bot]](https://avatars.githubusercontent.com/in/1144995?s=60&v=4){kind=small}
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: 4d379065e5
ℹ️ About Codex in GitHub
Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".
Use non-collapsible spacing entities in recursive tree prefixes so deeper last-child branches keep their visual nesting in markdown table renderers. Regenerated affected API reference docs. --- _Generated with `mux` • Model: `openai:gpt-5.3-codex` • Thinking: `xhigh` • Cost: `$0.56`_ <!-- mux-attribution: model=openai:gpt-5.3-codex thinking=xhigh costs=0.56 -->
|
@codex review Please take another look. |
|
Codex Review: Didn't find any major issues. Nice work! ℹ️ About Codex in GitHubYour team has set up Codex to review pull requests in this repo. Reviews are triggered when you
If Codex has suggestions, it will comment; otherwise it will react with 👍. Codex can also answer questions or update the PR. Try commenting "@codex address that feedback". |
1 participant
Summary
This PR improves generated API reference readability by rendering nested fields with explicit tree prefixes instead of invisible non-breaking-space indentation.
Background
We recently switched API docs to be more YAML-oriented, but nested structure was still hard to read in rendered markdown tables because indentation relied on
in table cells.Implementation
hack/crd-ref-docs/templates/markdown/gv_list.tpl: indentation with tree-style prefixes (├─,└─,│).docs/reference/api/codercontrolplane.mddocs/reference/api/coderprovisioner.mddocs/reference/api/workspaceproxy.mdValidation
make verify-vendormake testmake buildmake lintmake docs-buildmake docs-referenceRisks
Low. This change only affects markdown template output and generated docs. Runtime code paths are unchanged.
Generated with
mux• Model:openai:gpt-5.3-codex• Thinking:xhigh• Cost:$0.56